Three-dimensional data storage method, three-dimensional data acquisition method, three-dimensional data storage device, and three-dimensional data acquisition device

ABSTRACT

A three-dimensional data storage method includes: acquiring one or more units in which an encoded stream generated by encoding point cloud data is stored; and storing the one or more units into a file. The storing includes storing, in control information for the file, information indicating that data stored in the file is data generated by encoding the point cloud data.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a U.S. continuation application of PCT InternationalPatent Application Number PCT/JP2019/030842 filed on Aug. 6, 2019,claiming the benefit of priority of U.S. Provisional Patent ApplicationNo. 62/714,973 filed on Aug. 6, 2018, the entire contents of which arehereby incorporated by reference.

BACKGROUND 1. Technical Field

The present disclosure relates to a three-dimensional data storagemethod, a three-dimensional data acquisition method, a three-dimensionaldata storage device, and a three-dimensional data acquisition device.

2. Description of the Related Art

Devices or services utilizing three-dimensional data are expected tofind their widespread use in a wide range of fields, such as computervision that enables autonomous operations of cars or robots, mapinformation, monitoring, infrastructure inspection, and videodistribution. Three-dimensional data is obtained through various meansincluding a distance sensor such as a rangefinder, as well as a stereocamera and a combination of a plurality of monocular cameras.

Methods of representing three-dimensional data include a method known asa point cloud scheme that represents the shape of a three-dimensionalstructure by a point cloud in a three-dimensional space. In the pointcloud scheme, the positions and colors of a point cloud are stored.While point cloud is expected to be a mainstream method of representingthree-dimensional data, a massive amount of data of a point cloudnecessitates compression of the amount of three-dimensional data byencoding for accumulation and transmission, as in the case of atwo-dimensional moving picture (examples include Moving Picture ExpertsGroup-4 Advanced Video Coding (MPEG-4 AVC) and High Efficiency VideoCoding (HEVC) standardized by MPEG).

Meanwhile, point cloud compression is partially supported by, forexample, an open-source library (Point Cloud Library) for pointcloud-related processing.

Furthermore, a technique for searching for and displaying a facilitylocated in the surroundings of the vehicle by using three-dimensionalmap data is known (for example, see International Publication WO2014/020663).

SUMMARY

There has been a demand for reducing a processing amount or increasing aprocessing speed in devices processing three-dimensional data.

The present disclosure has an object to provide a three-dimensional datastorage method, a three-dimensional data acquisition method, athree-dimensional data storage device, or a three-dimensional dataacquisition device that allows a three-dimensional data processingdevice to reduce a processing amount or increase a processing speed.

In accordance with an aspect of the present disclosure, athree-dimensional data storage method includes: acquiring one or moreunits in which an encoded stream generated by encoding point cloud datais stored; and storing the one or more units into a file, wherein thestoring includes storing information in control information (signalinginformation) for the file, the information indicating that data storedin the file is data generated by encoding the point cloud data.

In accordance with an aspect of the present disclosure, athree-dimensional data acquisition method includes: acquiring a filestoring one or more units in which an encoded stream generated byencoding point cloud data is stored; and acquiring the one or more unitsfrom the file, wherein control information for the file includesinformation indicating that data stored in the file is data generated byencoding the point cloud data.

The present disclosure provides a three-dimensional data storage method,a three-dimensional data acquisition method, a three-dimensional datastorage device, or a three-dimensional data acquisition device thatallows a three-dimensional data processing device to reduce a processingamount or increase a processing speed.

BRIEF DESCRIPTION OF DRAWINGS

These and other objects, advantages and features of the disclosure willbecome apparent from the following description thereof taken inconjunction with the accompanying drawings that illustrate a specificembodiment of the present disclosure.

FIG. 1 is a diagram illustrating a configuration of a three-dimensionaldata encoding and decoding system according to Embodiment 1;

FIG. 2 is a diagram illustrating a structure example of point cloud dataaccording to Embodiment 1;

FIG. 3 is a diagram illustrating a structure example of a data fileindicating the point cloud data according to Embodiment 1;

FIG. 4 is a diagram illustrating types of the point cloud data accordingto Embodiment 1;

FIG. 5 is a diagram illustrating a structure of a first encoderaccording to Embodiment 1;

FIG. 6 is a block diagram illustrating the first encoder according toEmbodiment 1;

FIG. 7 is a diagram illustrating a structure of a first decoderaccording to Embodiment 1;

FIG. 8 is a block diagram illustrating the first decoder according toEmbodiment 1;

FIG. 9 is a diagram illustrating a structure of a second encoderaccording to Embodiment 1;

FIG. 10 is a block diagram illustrating the second encoder according toEmbodiment 1;

FIG. 11 is a diagram illustrating a structure of a second decoderaccording to Embodiment 1;

FIG. 12 is a block diagram illustrating the second decoder according toEmbodiment 1;

FIG. 13 is a diagram illustrating a protocol stack related to PCCencoded data according to Embodiment 1;

FIG. 14 is a diagram illustrating the protocol stack according toEmbodiment 1;

FIG. 15 is a diagram illustrating a syntax example of a NAL unitaccording to Embodiment 1;

FIG. 16 is a diagram illustrating a syntax example of a NAL unit headeraccording to Embodiment 1;

FIG. 17 is a diagram illustrating a semantics example of pec_codec_typeaccording to Embodiment 1;

FIG. 18 is a diagram illustrating a semantics example ofpcc_nal_unit_type according to Embodiment 1;

FIG. 19 is a flowchart of encoding processing according to Embodiment 1;

FIG. 20 is a flowchart of decoding processing by the second decoderaccording to Embodiment 1;

FIG. 21 is a flowchart of decoding processing by the first decoderaccording to Embodiment 1;

FIG. 22 is a diagram illustrating a protocol stack according toEmbodiment 2;

FIG. 23 is a diagram illustrating a syntax example of a NAL unit forcodec 2 according to Embodiment 2;

FIG. 24 is a diagram illustrating a syntax example of a NAL unit headerfor codec 2 according to Embodiment 2;

FIG. 25 is a diagram illustrating a semantics example ofcodec2_nal_unit_type according to Embodiment 2;

FIG. 26 is a diagram illustrating a syntax example of a NAL unit forcodec 1 according to Embodiment 2;

FIG. 27 is a diagram illustrating a syntax example of a NAL unit headerfor codec 1 according to Embodiment 2;

FIG. 28 is a diagram illustrating a semantics example ofcodec1_nal_unit_type according to Embodiment 2;

FIG. 29 is a flowchart of encoding processing according to Embodiment 2;

FIG. 30 is a flowchart of decoding processing according to Embodiment 2;

FIG. 31 is a diagram illustrating a protocol stack according toEmbodiment 3;

FIG. 32 is a diagram illustrating a syntax example of a NAL unitaccording to Embodiment 3;

FIG. 33 is a diagram illustrating a syntax example of a NAL unit headeraccording to Embodiment 3;

FIG. 34 is a diagram illustrating a semantics example ofpcc_nal_unit_type according to Embodiment 3;

FIG. 35 is a flowchart of encoding processing according to Embodiment 3;

FIG. 36 is a flowchart of decoding processing according to Embodiment 3;

FIG. 37 is a flowchart of encoding processing according to Variation ofEmbodiment;

FIG. 38 is a flowchart of decoding processing according to Variation ofEmbodiment;

FIG. 39 is a block diagram of an encoder according to Embodiment 4;

FIG. 40 is a block diagram of a decoder according to Embodiment 4;

FIG. 41 is a flowchart of encoding processing according to Embodiment 4;

FIG. 42 is a flowchart of decoding processing according to Embodiment 4;

FIG. 43 is a diagram illustrating a basic structure of ISOBMFF accordingto Embodiment 5;

FIG. 44 is a diagram illustrating a protocol stack according toEmbodiment 5;

FIG. 45 is a diagram illustrating an example where a NAL unit is storedin a file for codec 1 according to Embodiment 5;

FIG. 46 is a diagram illustrating an example where a NAL unit is storedin a file for codec 2 according to Embodiment 5;

FIG. 47 is a diagram illustrating a structure of a first multiplexeraccording to Embodiment 5;

FIG. 48 is a diagram illustrating a structure of a first demultiplexeraccording to Embodiment 5;

FIG. 49 is a diagram illustrating a structure of a second multiplexeraccording to Embodiment 5;

FIG. 50 is a diagram illustrating a structure of a second demultiplexeraccording to Embodiment 5;

FIG. 51 is a flowchart of processing performed by the first multiplexeraccording to Embodiment 5;

FIG. 52 is a flowchart of processing performed by the second multiplexeraccording to Embodiment 5;

FIG. 53 is a flowchart of processing performed by the firstdemultiplexer and the first decoder according to Embodiment 5;

FIG. 54 is a flowchart of processing performed by the seconddemultiplexer and the second decoder according to Embodiment 5;

FIG. 55 is a diagram illustrating structures of an encoder and a thirdmultiplexer according to Embodiment 6;

FIG. 56 is a diagram illustrating structures of a third demultiplexerand a decoder according to Embodiment 6;

FIG. 57 is a flowchart of processing performed by the third multiplexeraccording to Embodiment 6;

FIG. 58 is a flowchart of processing performed by the thirddemultiplexer and the decoder according to Embodiment 6;

FIG. 59 is a flowchart of processing performed by a three-dimensionaldata storage device according to Embodiment 6; and

FIG. 60 is a flowchart of processing performed by a three-dimensionaldata acquisition device according to Embodiment 6.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In accordance with an aspect of the present disclosure, athree-dimensional data storage method includes: acquiring one or moreunits in which an encoded stream generated by encoding point cloud datais stored; and storing the one or more units into a file, wherein thestoring includes storing information in control information for thefile, the information indicating that data stored in the file is datagenerated by encoding the point cloud data.

The three-dimensional data storage method allows a device that processesa file generated by the method to early determine, with reference tocontrol information for the file, whether or not data stored in the fileis encoded data of point cloud data. It is therefore possible to reducea processing amount or increase a processing speed of the device.

For example, it is possible that the information further indicates anencoding method used in the encoding of the point cloud data out of afirst encoding method and a second encoding method.

The three-dimensional data storage method allows a device that processesa file generated by the method to early determine a codec used for datastored in the file, with reference to control information for the file.It is therefore possible to reduce a processing amount or increase aprocessing speed of the device.

For example, it is also possible that the first encoding method is ascheme for encoding geometry information representing a position of thepoint cloud data by an N-ary tree, and encoding attribute informationwith reference to the geometry information, where N is an integer equalto or greater than 2, and the second encoding method is a scheme forgenerating a two-dimensional image from the point cloud data, andencoding the two-dimensional image using a video encoding method.

For example, it is further possible that the file is in conformity withISO Based Media File Format (ISOBMFF).

In accordance with another aspect of the present disclosure, athree-dimensional data acquisition method includes: acquiring a filestoring one or more units in which an encoded stream generated byencoding point cloud data is stored; and acquiring the one or more unitsfrom the file, wherein control information for the file includesinformation indicating that data stored in the file is data generated byencoding the point cloud data.

The three-dimensional data acquisition method makes it possible to earlydetermine whether or not data stored in a file is encoded data of pointcloud data. It is therefore possible to reduce a processing amount orincrease a processing speed of a device performing the method or devicesin the subsequent stages.

For example, it is possible that the information further indicates anencoding method used in the encoding of the point cloud data out of afirst encoding method and a second encoding method.

The three-dimensional data acquisition method makes it possible to earlydetermine a codec used for data stored in the file, with reference tocontrol information for the file. It is therefore possible to reduce aprocessing amount or increase a processing speed of a device performingthe method or devices in the subsequent stages.

For example, it is also possible that the three-dimensional dataacquisition method further includes: acquiring, with reference to theinformation, one of data encoded by the first encoding method and dataencoded using the second encoding method from the point cloud data thatis encoded.

For example, it is further possible that the first encoding method is ascheme for encoding geometry information representing a position of thepoint cloud data by an N-ary tree, and encoding attribute informationwith reference to the geometry information, where N is an integer equalto or greater than 2, and that the second encoding method is a schemefor generating a two-dimensional image from the point cloud data, andencoding the two-dimensional image using a video encoding method.

For example, it is further possible that the file is in conformity withISOBMFF.

In accordance with still another aspect of the present disclosure, athree-dimensional data storage device, comprising: a processor; andmemory wherein, using the memory, the processor: acquires one or moreunits in which an encoded stream generated by encoding point cloud datais stored; and stores the one or more units into a file, wherein thestoring includes storing information in control information for thefile, the information indicating that data stored in the file is datagenerated by encoding the point cloud data.

The three-dimensional data storage device allows a device that processesa file generated by the three-dimensional data storage method to earlydetermine, with reference to control information for the file, whetheror not data stored in the file is encoded data of point cloud data. Itis therefore possible to reduce a processing amount or increase aprocessing speed of the device processing the file.

In accordance with still another aspect of the present disclosure, athree-dimensional data acquisition device includes: a processor; andmemory, wherein, using the memory, the processor: acquires a filestoring one or more units in which an encoded stream generated byencoding point cloud data is stored; and acquires the one or more unitsfrom the file, wherein control information for the file includesinformation indicating that data stored in the file is data generated byencoding the point cloud data.

The three-dimensional data acquisition device makes it possible to earlydetermine whether or not data stored in a file is encoded data of pointcloud data. It is therefore possible to reduce a processing amount orincrease a processing speed of three-dimensional data acquisition deviceor devices in the subsequent stages.

Note that these general or specific aspects may be implemented as asystem, a method, an integrated circuit, a computer program, or acomputer-readable recording medium such as a Compact Disc Read OnlyMemory (CD-ROM), or may be implemented as any combination of a system, amethod, an integrated circuit, a computer program, and a recordingmedium.

The following describes embodiments with reference to the drawings. Notethat the following embodiments show exemplary embodiments of the presentdisclosure. The numerical values, shapes, materials, structuralcomponents, the arrangement and connection of the structural components,steps, the processing order of the steps, etc. shown in the followingembodiments are mere examples, and thus are not intended to limit thepresent disclosure. Of the structural components described in thefollowing embodiments, structural components not recited in any one ofthe independent claims that indicate the broadest concepts will bedescribed as optional structural components.

Embodiment 1

When using encoded data of a point cloud in a device or for a service inpractice, required information for the application is desirablytransmitted and received in order to reduce the network bandwidth.However, conventional encoding structures for three-dimensional datahave no such a function, and there is also no encoding method for such afunction.

Embodiment 1 described below relates to a three-dimensional dataencoding method and a three-dimensional data encoding device for encodeddata of a three-dimensional point cloud that provides a function oftransmitting and receiving required information for an application, athree-dimensional data decoding method and a three-dimensional datadecoding device for decoding the encoded data, a three-dimensional datamultiplexing method for multiplexing the encoded data, and athree-dimensional data transmission method for transmitting the encodeddata.

In particular, at present, a first encoding method and a second encodingmethod are under investigation as encoding methods (encoding schemes)for point cloud data. However, there is no method defined for storingthe configuration of encoded data and the encoded data in a systemformat. Thus, there is a problem that an encoder cannot perform an MUXprocess (multiplexing), transmission, or accumulation of data.

In addition, there is no method for supporting a format that involvestwo codecs, the first encoding method and the second encoding method,such as Point Cloud Compression (PCC).

With regard to this embodiment, a configuration of PCC-encoded data thatinvolves two codecs, a first encoding method and a second encodingmethod, and a method of storing the encoded data in a system format willbe described.

A configuration of a three-dimensional data (point cloud data) encodingand decoding system according to this embodiment will be firstdescribed. FIG. 1 is a diagram showing an example of a configuration ofthe three-dimensional data encoding and decoding system according tothis embodiment. As shown in FIG. 1, the three-dimensional data encodingand decoding system includes three-dimensional data encoding system4601, three-dimensional data decoding system 4602, sensor terminal 4603,and external connector 4604.

Three-dimensional data encoding system 4601 generates encoded data ormultiplexed data by encoding point cloud data, which isthree-dimensional data. Three-dimensional data encoding system 4601 maybe a three-dimensional data encoding device implemented by a singledevice or a system implemented by a plurality of devices. Thethree-dimensional data encoding device may include a part of a pluralityof processors included in three-dimensional data encoding system 4601.

Three-dimensional data encoding system 4601 includes point cloud datageneration system 4611, presenter 4612, encoder 4613, multiplexer 4614,input/output unit 4615, and controller 4616. Point cloud data generationsystem 4611 includes sensor information obtainer 4617, and point clouddata generator 4618.

Sensor information obtainer 4617 obtains sensor information from sensorterminal 4603, and outputs the sensor information to point cloud datagenerator 4618. Point cloud data generator 4618 generates point clouddata from the sensor information, and outputs the point cloud data toencoder 4613.

Presenter 4612 presents the sensor information or point cloud data to auser. For example, presenter 4612 displays information or an image basedon the sensor information or point cloud data.

Encoder 4613 encodes (compresses) the point cloud data, and outputs theresulting encoded data, control information (signaling information)obtained in the course of the encoding, and other additional informationto multiplexer 4614. The additional information includes the sensorinformation, for example.

Multiplexer 4614 generates multiplexed data by multiplexing the encodeddata, the control information, and the additional information inputthereto from encoder 4613. A format of the multiplexed data is a fileformat for accumulation or a packet format for transmission, forexample.

Input/output unit 4615 (a communication unit or interface, for example)outputs the multiplexed data to the outside. Alternatively, themultiplexed data may be accumulated in an accumulator, such as aninternal memory. Controller 4616 (or an application executor) controlseach processor. That is, controller 4616 controls the encoding, themultiplexing, or other processing.

Note that the sensor information may be input to encoder 4613 ormultiplexer 4614. Alternatively, input/output unit 4615 may output thepoint cloud data or encoded data to the outside as itis.

A transmission signal (multiplexed data) output from three-dimensionaldata encoding system 4601 is input to three-dimensional data decodingsystem 4602 via external connector 4604.

Three-dimensional data decoding system 4602 generates point cloud data,which is three-dimensional data, by decoding the encoded data ormultiplexed data. Note that three-dimensional data decoding system 4602may be a three-dimensional data decoding device implemented by a singledevice or a system implemented by a plurality of devices. Thethree-dimensional data decoding device may include a part of a pluralityof processors included in three-dimensional data decoding system 4602.

Three-dimensional data decoding system 4602 includes sensor informationobtainer 4621, input/output unit 4622, demultiplexer 4623, decoder 4624,presenter 4625, user interface 4626, and controller 4627.

Sensor information obtainer 4621 obtains sensor information from sensorterminal 4603.

Input/output unit 4622 obtains the transmission signal, decodes thetransmission signal into the multiplexed data (file format or packet),and outputs the multiplexed data to demultiplexer 4623.

Demultiplexer 4623 obtains the encoded data, the control information,and the additional information from the multiplexed data, and outputsthe encoded data, the control information, and the additionalinformation to decoder 4624.

Decoder 4624 reconstructs the point cloud data by decoding the encodeddata.

Presenter 4625 presents the point cloud data to a user. For example,presenter 4625 displays information or an image based on the point clouddata. User interface 4626 obtains an indication based on a manipulationby the user. Controller 4627 (or an application executor) controls eachprocessor. That is, controller 4627 controls the demultiplexing, thedecoding, the presentation, or other processing.

Note that input/output unit 4622 may obtain the point cloud data orencoded data as it is from the outside. Presenter 4625 may obtainadditional information, such as sensor information, and presentinformation based on the additional information. Presenter 4625 mayperform a presentation based on an indication from a user obtained onuser interface 4626.

Sensor terminal 4603 generates sensor information, which is informationobtained by a sensor. Sensor terminal 4603 is a terminal provided with asensor or a camera. For example, sensor terminal 4603 is a mobile bodysuch as an automobile, a flying object, such as an aircraft, a mobileterminal, or a camera.

Sensor information that can be generated by sensor terminal 4603includes (1) the distance between sensor terminal 4603 and an object orthe reflectance of the object obtained by LIDAR, a millimeter waveradar, or an infrared sensor or (2) the distance between a camera and anobject or the reflectance of the object obtained by a plurality ofmonocular camera images or a stereo-camera image, for example. Thesensor information may include the posture, orientation, gyro (angularvelocity), position (GPS information or altitude), velocity oracceleration of the sensor, for example. The sensor information mayinclude air temperature, air pressure, air humidity or magnetism, forexample.

External connector 4604 is implemented by an integrated circuit (LSI orIC), an external accumulator, communication with a cloud server via theInternet, or broadcasting, for example.

Next, point cloud data will be described. FIG. 2 is a diagram showing aconfiguration of point cloud data. FIG. 3 is a diagram showing aconfiguration example of a data file describing information of the pointcloud data.

Point cloud data includes data on a plurality of points. Data on eachpoint includes geometry information (three-dimensional coordinates) andattribute information associated with the geometry information. A set ofa plurality of such points is referred to as a point cloud. For example,a point cloud indicates a three-dimensional shape of an object.

Geometry information (position), such as three-dimensional coordinates,may be referred to as geometry. Data on each point may include attributeinformation (attribute) on a plurality of types of attributes. A type ofattribute is color or reflectance, for example.

One piece of attribute information may be associated with one piece ofgeometry information, or attribute information on a plurality ofdifferent types of attributes may be associated with one piece ofgeometry information. Alternatively, a plurality of pieces of attributeinformation on the same type of attribute may be associated with onepiece of geometry information.

The configuration example of a data file shown in FIG. 3 is an examplein which geometry information and attribute information are associatedwith each other in a one-to-one relationship, and geometry informationand attribute information on N points forming point cloud data areshown.

The geometry information is information on three axes, specifically anx-axis, a y-axis, and a z-axis, for example. The attribute informationis RGB color information, for example. A representative data file is plyfile, for example.

Next, types of point cloud data will be described. FIG. 4 is a diagramshowing types of point cloud data. As shown in FIG. 4, point cloud dataincludes a static object and a dynamic object.

The static object is three-dimensional point cloud data at an arbitrarytime (a time point). The dynamic object is three-dimensional point clouddata that varies with time. In the following, three-dimensional pointcloud data associated with a time point will be referred to as a PCCframe or a frame.

The object may be a point cloud whose range is limited to some extent,such as ordinary video data, or may be a large point cloud whose rangeis not limited, such as map information.

There are point cloud data having varying densities. There may be sparsepoint cloud data and dense point cloud data.

In the following, each processor will be described in detail. Sensorinformation is obtained by various means, including a distance sensorsuch as LIDAR or a range finder, a stereo camera, or a combination of aplurality of monocular cameras. Point cloud data generator 4618generates point cloud data based on the sensor information obtained bysensor information obtainer 4617. Point cloud data generator 4618generates geometry information as point cloud data, and adds attributeinformation associated with the geometry information to the geometryinformation.

When generating geometry information or adding attribute information,point cloud data generator 4618 may process the point cloud data. Forexample, point cloud data generator 4618 may reduce the data amount byomitting a point cloud whose position coincides with the position ofanother point cloud. Point cloud data generator 4618 may also convertthe geometry information (such as shifting, rotating or normalizing theposition) or render the attribute information.

Note that, although FIG. 1 shows point cloud data generation system 4611as being included in three-dimensional data encoding system 4601, pointcloud data generation system 4611 may be independently provided outsidethree-dimensional data encoding system 4601.

Encoder 4613 generates encoded data by encoding point cloud dataaccording to an encoding method previously defined. In general, thereare the two types of encoding methods described below. One is anencoding method using geometry information, which will be referred to asa first encoding method, hereinafter. The other is an encoding methodusing a video codec, which will be referred to as a second encodingmethod, hereinafter.

Decoder 4624 decodes the encoded data into the point cloud data usingthe encoding method previously defined.

Multiplexer 4614 generates multiplexed data by multiplexing the encodeddata in an existing multiplexing method. The generated multiplexed datais transmitted or accumulated. Multiplexer 4614 multiplexes not only thePCC-encoded data but also another medium, such as a video, an audio,subtitles, an application, or a file, or reference time information.Multiplexer 4614 may further multiplex attribute information associatedwith sensor information or point cloud data.

Multiplexing schemes or file formats include ISOBMFF, MPEG-DASH, whichis a transmission scheme based on ISOBMFF, MMT, MPEG-2 TS Systems, orRMP, for example.

Demultiplexer 4623 extracts PCC-encoded data, other media, timeinformation and the like from the multiplexed data.

Input/output unit 4615 transmits the multiplexed data in a methodsuitable for the transmission medium or accumulation medium, such asbroadcasting or communication. Input/output unit 4615 may communicatewith another device over the Internet or communicate with anaccumulator, such as a cloud server.

As a communication protocol, http, ftp, TCP, UDP or the like is used.The pull communication scheme or the push communication scheme can beused.

A wired transmission or a wireless transmission can be used. For thewired transmission, Ethernet (registered trademark), USB, RS-232C, HDMI(registered trademark), or a coaxial cable is used, for example. For thewireless transmission, wireless LAN, Wi-Fi (registered trademark),Bluetooth (registered trademark), or a millimeter wave is used, forexample.

As a broadcasting scheme, DVB-T2, DVB-S2, DVB-C2, ATSC3.0, or ISDB-S3 isused, for example.

FIG. 5 is a diagram showing a configuration of first encoder 4630, whichis an example of encoder 4613 that performs encoding in the firstencoding method. FIG. 6 is a block diagram showing first encoder 4630.First encoder 4630 generates encoded data (encoded stream) by encodingpoint cloud data in the first encoding method. First encoder 4630includes geometry information encoder 4631, attribute informationencoder 4632, additional information encoder 4633, and multiplexer 4634.

First encoder 4630 is characterized by performing encoding by keeping athree-dimensional structure in mind. First encoder 4630 is furthercharacterized in that attribute information encoder 4632 performsencoding using information obtained from geometry information encoder4631. The first encoding method is referred to also as geometry-basedPCC (GPCC).

Point cloud data is PCC point cloud data like a PLY file or PCC pointcloud data generated from sensor information, and includes geometryinformation (position), attribute information (attribute), and otheradditional information (metadata). The geometry information is input togeometry information encoder 4631, the attribute information is input toattribute information encoder 4632, and the additional information isinput to additional information encoder 4633.

Geometry information encoder 4631 generates encoded geometry information(compressed geometry), which is encoded data, by encoding geometryinformation. For example, geometry information encoder 4631 encodesgeometry information using an N-ary tree structure, such as an octree.Specifically in the case of an octree, a current space is divided intoeight nodes (subspaces), 8-bit information (occupancy code) thatindicates whether each node includes a point cloud or not is generated.Anode including a point cloud is further divided into eight nodes, and8-bit information that indicates whether each of the eight nodesincludes a point cloud or not is generated. This process is repeateduntil a predetermined level is reached or the number of the point cloudsincluded in each node becomes equal to or less than a threshold.

Attribute information encoder 4632 generates encoded attributeinformation (compressed attribute), which is encoded data, by encodingattribute information using configuration information generated bygeometry information encoder 4631. For example, attribute informationencoder 4632 determines a reference point (reference node) that is to bereferred to in encoding a current point (current node) to be processedbased on the octree structure generated by geometry information encoder4631. For example, attribute information encoder 4632 refers to a nodewhose parent node in the octree is the same as the parent node of thecurrent node, of peripheral nodes or neighboring nodes. Note that themethod of determining a reference relationship is not limited to thismethod.

The process of encoding attribute information may include at least oneof a quantization process, a prediction process, and an arithmeticencoding process. In this case, “refer to” means using a reference nodefor calculating a predicted value of attribute information or using astate of a reference node (occupancy information that indicates whethera reference node includes a point cloud or not, for example) fordetermining a parameter of encoding. For example, the parameter ofencoding is a quantization parameter in the quantization process or acontext or the like in the arithmetic encoding.

Additional information encoder 4633 generates encoded additionalinformation (compressed metadata), which is encoded data, by encodingcompressible data of additional information.

Multiplexer 4634 generates encoded stream (compressed stream), which isencoded data, by multiplexing encoded geometry information, encodedattribute information, encoded additional information, and otheradditional information. The generated encoded stream is output to aprocessor in a system layer (not shown).

Next, first decoder 4640, which is an example of decoder 4624 thatperforms decoding in the first encoding method, will be described. FIG.7 is a diagram showing a configuration of first decoder 4640. FIG. 8 isa block diagram showing first decoder 4640. First decoder 4640 generatespoint cloud data by decoding encoded data (encoded stream) encoded inthe first encoding method in the first encoding method. First decoder4640 includes demultiplexer 4641, geometry information decoder 4642,attribute information decoder 4643, and additional information decoder4644.

An encoded stream (compressed stream), which is encoded data, is inputto first decoder 4640 from a processor in a system layer (not shown).

Demultiplexer 4641 separates encoded geometry information (compressedgeometry), encoded attribute information (compressed attribute), encodedadditional information (compressed metadata), and other additionalinformation from the encoded data.

Geometry information decoder 4642 generates geometry information bydecoding the encoded geometry information. For example, geometryinformation decoder 4642 restores the geometry information on a pointcloud represented by three-dimensional coordinates from encoded geometryinformation represented by an N-ary structure, such as an octree.

Attribute information decoder 4643 decodes the encoded attributeinformation based on configuration information generated by geometryinformation decoder 4642. For example, attribute information decoder4643 determines a reference point (reference node) that is to bereferred to in decoding a current point (current node) to be processedbased on the octree structure generated by geometry information decoder4642. For example, attribute information decoder 4643 refers to a nodewhose parent node in the octree is the same as the parent node of thecurrent node, of peripheral nodes or neighboring nodes. Note that themethod of determining a reference relationship is not limited to thismethod.

The process of decoding attribute information may include at least oneof an inverse quantization process, a prediction process, and anarithmetic decoding process. In this case, “refer to” means using areference node for calculating a predicted value of attributeinformation or using a state of a reference node (occupancy informationthat indicates whether a reference node includes a point cloud or not,for example) for determining a parameter of decoding. For example, theparameter of decoding is a quantization parameter in the inversequantization process or a context or the like in the arithmeticdecoding.

Additional information decoder 4644 generates additional information bydecoding the encoded additional information. First decoder 4640 usesadditional information required for the decoding process for thegeometry information and the attribute information in the decoding, andoutputs additional information required for an application to theoutside.

Next, second encoder 4650, which is an example of encoder 4613 thatperforms encoding in the second encoding method, will be described. FIG.9 is a diagram showing a configuration of second encoder 4650. FIG. 10is a block diagram showing second encoder 4650.

Second encoder 4650 generates encoded data (encoded stream) by encodingpoint cloud data in the second encoding method. Second encoder 4650includes additional information generator 4651, geometry image generator4652, attribute image generator 4653, video encoder 4654, additionalinformation encoder 4655, and multiplexer 4656.

Second encoder 4650 is characterized by generating a geometry image andan attribute image by projecting a three-dimensional structure onto atwo-dimensional image, and encoding the generated geometry image andattribute image in an existing video encoding scheme. The secondencoding method is referred to as video-based PCC (VPCC).

Point cloud data is PCC point cloud data like a PLY file or PCC pointcloud data generated from sensor information, and includes geometryinformation (position), attribute information (attribute), and otheradditional information (metadata).

Additional information generator 4651 generates map information on aplurality of two-dimensional images by projecting a three-dimensionalstructure onto a two-dimensional image.

Geometry image generator 4652 generates a geometry image based on thegeometry information and the map information generated by additionalinformation generator 4651. The geometry image is a distance image inwhich distance (depth) is indicated as a pixel value, for example. Thedistance image may be an image of a plurality of point clouds viewedfrom one point of view (an image of a plurality of point cloudsprojected onto one two-dimensional plane), a plurality of images of aplurality of point clouds viewed from a plurality of points of view, ora single image integrating the plurality of images.

Attribute image generator 4653 generates an attribute image based on theattribute information and the map information generated by additionalinformation generator 4651. The attribute image is an image in whichattribute information (color (RGB), for example) is indicated as a pixelvalue, for example. The image may be an image of a plurality of pointclouds viewed from one point of view (an image of a plurality of pointclouds projected onto one two-dimensional plane), a plurality of imagesof a plurality of point clouds viewed from a plurality of points ofview, or a single image integrating the plurality of images.

Video encoder 4654 generates an encoded geometry image (compressedgeometry image) and an encoded attribute image (compressed attributeimage), which are encoded data, by encoding the geometry image and theattribute image in a video encoding scheme. Note that, as the videoencoding scheme, any well-known encoding method can be used. Forexample, the video encoding scheme is AVC or HEVC.

Additional information encoder 4655 generates encoded additionalinformation (compressed metadata) by encoding the additionalinformation, the map information and the like included in the pointcloud data.

Multiplexer 4656 generates an encoded stream (compressed stream), whichis encoded data, by multiplexing the encoded geometry image, the encodedattribute image, the encoded additional information, and otheradditional information. The generated encoded stream is output to aprocessor in a system layer (not shown).

Next, second decoder 4660, which is an example of decoder 4624 thatperforms decoding in the second encoding method, will be described. FIG.11 is a diagram showing a configuration of second decoder 4660. FIG. 12is a block diagram showing second decoder 4660. Second decoder 4660generates point cloud data by decoding encoded data (encoded stream)encoded in the second encoding method in the second encoding method.Second decoder 4660 includes demultiplexer 4661, video decoder 4662,additional information decoder 4663, geometry information generator4664, and attribute information generator 4665.

An encoded stream (compressed stream), which is encoded data, is inputto second decoder 4660 from a processor in a system layer (not shown).

Demultiplexer 4661 separates an encoded geometry image (compressedgeometry image), an encoded attribute image (compressed attributeimage), an encoded additional information (compressed metadata), andother additional information from the encoded data.

Video decoder 4662 generates a geometry image and an attribute image bydecoding the encoded geometry image and the encoded attribute image in avideo encoding scheme. Note that, as the video encoding scheme, anywell-known encoding method can be used. For example, the video encodingscheme is AVC or HEVC.

Additional information decoder 4663 generates additional informationincluding map information or the like by decoding the encoded additionalinformation.

Geometry information generator 4664 generates geometry information fromthe geometry image and the map information. Attribute informationgenerator 4665 generates attribute information from the attribute imageand the map information.

Second decoder 4660 uses additional information required for decoding inthe decoding, and outputs additional information required for anapplication to the outside.

In the following, a problem with the PCC encoding scheme will bedescribed. FIG. 13 is a diagram showing a protocol stack relating toPCC-encoded data. FIG. 13 shows an example in which PCC-encoded data ismultiplexed with other medium data, such as a video (HEVC, for example)or an audio, and transmitted or accumulated.

A multiplexing scheme and a file format have a function of multiplexingvarious encoded data and transmitting or accumulating the data. Totransmit or accumulate encoded data, the encoded data has to beconverted into a format for the multiplexing scheme. For example, withHEVC, a technique for storing encoded data in a data structure referredto as a NAL unit and storing the NAL unit in ISOBMFF is prescribed.

At present, a first encoding method (Codec1) and a second encodingmethod (Codec2) are under investigation as encoding methods for pointcloud data. However, there is no method defined for storing theconfiguration of encoded data and the encoded data in a system format.Thus, there is a problem that an encoder cannot perform an MUX process(multiplexing), transmission, or accumulation of data.

Note that, in the following, the term “encoding method” means any of thefirst encoding method and the second encoding method unless a particularencoding method is specified.

In the following, a way of defining a NAL unit according to thisembodiment will be described. For example, with a conventional codec,such as HEVC, a NAL unit in one format is defined for one codec.However, there has been no method that supports a format that involvestwo codecs, that is, the first encoding method and the second encodingmethod, such as PCC (such a codec will be referred to as a PCC codec,hereinafter).

In this embodiment, a format that is common to the PCC codecs is definedfor a NAL unit, and an identifier of a NAL unit that depends on the PCCcodec is also defined. FIG. 14 is a diagram showing a protocol stack insuch a case. FIGS. 15 to 17 are diagrams illustrating an example of aNAL unit format common to the codecs. FIG. 15 is a diagram showing asyntax example of a common PCC NAL unit. FIG. 16 is a diagram showing asyntax example of a common PCC NAL unit header. FIG. 17 is a diagramshowing a semantics example of pcc_codec_type. FIG. 18 is a diagramshowing a semantics example of pcc_nal_unit_type, and shows an exampleof definitions of the NAL unit type that depends on the codec.

As a NAL unit format, a NAL unit format that is common to the PCC codecsis defined. A NAL unit (pec_nal_unit) includes a header(pcc_nal_unit_header), a payload (pcc_nal_unit_payload), and a trailingbit (trailing_bits). Regardless of the codec, that is, whether data isto be stored in the first encoding method or the second encoding method,the same format is used.

In the NAL unit header (pcc_nal_unit_header), a codec type(pcc_codec_type) and a NAL unit type (pcc_nal_unit_type) are stored. Thecodec type indicates whether the PCC codec of the encoded data to bestored in the NAL unit is the first encoding method or the secondencoding method.

The NAL unit type indicates the type of the NAL unit that depends on thecodec, and the type is defined for each codec. If the codec type is thefirst encoding method, the NAL unit type indicates a NAL unit typedefined for the first encoding method. If the codec type is the secondencoding method, the NAL unit type indicates a NAL unit type defined forthe second encoding method. That is, the NAL unit type defined for thefirst encoding method and the NAL unit type defined for the secondencoding method are associated with different meanings with the samevalue.

Note that, in the header, the function of the codec type may be mergedwith the NAL unit type. For example, a part of the information of theNAL unit type may be used to indicate the codec type.

Next, an encoding process according to this embodiment will bedescribed. FIG. 19 is a flowchart showing an encoding process accordingto this embodiment. The process in the drawing is a process performed byfirst encoder 4630 or second encoder 4650 defined as described above. Inthe following, first encoder 4630 and second encoder 4650 may not bediscriminated, and the encoder may be referred to as encoder 4613. Theprocess in the drawing is mainly performed by multiplexer 4634 shown inFIG. 6 or multiplexer 4656 shown in FIG. 10.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod, and it is supposed that which PCC codec is used for the encodingis known. For example, a user, an external device or the like mayspecify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, thefirst encoding method or the second encoding method (S4601).

When the codec used is the second encoding method (if “second encodingmethod” in S4602), encoder 4613 sets pcc_codec_type in the NAL unitheader to a value that indicates that data included in the payload ofthe NAL unit is data encoded in the second encoding method (S4603).Furthermore, encoder 4613 sets pcc_nal_unit_type in the NAL unit headerto the identifier of the NAL unit for the second encoding method(S4604). Encoder 4613 then generates a NAL unit having the set NAL unitheader and including the encoded data in the payload. Encoder 4613 thentransmits the generated NAL unit (S4605).

On the other hand, when the codec used is the first encoding method (if“first encoding method” in S4602), encoder 4613 sets pcc_codec_type inthe NAL unit header to a value that indicates that data included in thepayload of the NAL unit is data encoded in the first encoding method(S4606). Furthermore, encoder 4613 sets pcc_nal_unit_type in the NALunit header to the identifier of the NAL unit for the first encodingmethod (S4607). Encoder 4613 then generates a NAL unit having the setNAL unit header and including the encoded data in the payload. Encoder4613 then transmits the generated NAL unit (S4605).

If the function of pcc_codec_type is included in pcc_nal_unit_type instep S4603 or S4606, encoder 4613 may set pec_nal_unit_type to indicatewhether the codec for the NAL unit is the first encoding method or thesecond encoding method.

Next, a decoding process by first decoder 4640 or second decoder 4660according to this embodiment will be described. FIG. 20 is a flowchartshowing a decoding process by second decoder 4660. The process in thedrawing is mainly performed by demultiplexer 4661 shown in FIG. 12.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the second encoding method and the first encodingmethod. In this scheme, demultiplexer 4661 in second decoder 4660 canidentify the codec type of the NAL unit by referring to informationincluded in the NAL unit header. Therefore, demultiplexer 4661 canoutput required information to video decoder 4662 according to the codectype.

First, second decoder 4660 receives a NAL unit (S4611). For example, theNAL unit is the NAL unit generated in the process by encoder 4613described above. That is, the header of the NAL unit includespcc_codec_type and pcc_nal_unit_type.

Second decoder 4660 then determines whether pcc_codec_type in the NALunit header indicates the first encoding method or the second encodingmethod (S4612).

When pcc_codec_type indicates the second encoding method (if “secondencoding method” in S4612), second decoder 4660 determines that the dataincluded in the payload of the NAL unit is data encoded in the secondencoding method (S4613). Second decoder 4660 then identifies the databased on the determination that pcc_nal_unit_type in the NAL unit headeris the identifier of the NAL unit for the second encoding method(S4614). Second decoder 4660 then decodes the PCC data in a decodingprocess for the second encoding method (S4615).

On the other hand, when pcc_codec_type indicates the first encodingmethod (if “first encoding method” in S4612), second decoder 4660determines that the data included in the payload of the NAL unit is dataencoded in the first encoding method (S4616). In this case, seconddecoder 4660 does not process the NAL unit (S4617).

If the function of pcc_codec_type is included in pcc_nal_unit_type instep S4612, second decoder 4660 may refer to pec_nal_unit_type todetermine whether the codec used for the data included in the NAL unitis the first encoding method or the second encoding method.

FIG. 21 is a flowchart showing a decoding process by first decoder 4640.The process in the drawing is mainly performed by demultiplexer 4641shown in FIG. 8.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod. In this scheme, demultiplexer 4641 in first decoder 4640 canidentify the codec type of the NAL unit by referring to informationincluded in the NAL unit header. Therefore, demultiplexer 4641 canoutput required information to geometry information decoder 4642 andattribute information decoder 4643 according to the codec type.

First, first decoder 4640 receives a NAL unit (S4621). For example, theNAL unit is the NAL unit generated in the process by encoder 4613described above. That is, the header of the NAL unit includespcc_codec_type and pcc_nal_unit_type.

First decoder 4640 then determines whether pcc_codec_type in the NALunit header indicates the first encoding method or the second encodingmethod (S4622).

When pec_codec_type indicates the second encoding method (if “secondencoding method” in S4622), first decoder 4640 determines that the dataincluded in the payload of the NAL unit is data encoded in the secondencoding method (S4623). In this case, first decoder 4640 does notprocess the NAL unit (S4624).

On the other hand, when pcc_codec_type indicates the first encodingmethod (if “first encoding method” in S4622), first decoder 4640determines that the data included in the payload of the NAL unit is dataencoded in the first encoding method (S4625). First decoder 4640 thenidentifies the data based on the determination that pcc_nal_unit_type inthe NAL unit header is the identifier of the NAL unit for the firstencoding method (S4626). First decoder 4640 then decodes the PCC data ina decoding process for the first encoding method (S4627).

Embodiment 2

In Embodiment 2, another way of defining a NAL unit will be described.In this embodiment, for a NAL unit, different formats are defined fordifferent PCC codecs. Furthermore, an identifier of the NAL unit isindependently defined for each PCC codec.

FIG. 22 is a diagram showing a protocol stack in this case. FIG. 23 is adiagram showing a syntax example of a NAL unit (codec2_nal_unit) forcodec 2.

FIG. 24 is a diagram showing a syntax example of a NAL unit header(codec2_nal_unit_header) for codec 2. FIG. 25 is a diagram showing asemantics example of codec2_nal_unit_type.

FIG. 26 is a diagram showing a syntax example of a NAL unit(codec1_nal_unit) for codec 1. FIG. 27 is a diagram showing a syntaxexample of a NAL unit header (codec1_nal_unit_header) for codec 1. FIG.28 is a diagram showing a semantics example of codec1_nal_unit_type.

A NAL unit format is independently defined for each PCC codec. A NALunit (codec1_nal_unit, codec2_nal_unit) includes a header(codec1_nal_unit_header, codec2_nal_unit_header), a payload(codec1_nal_unit_payload, codec2_nal_unit_payload), and a trailing bit(trailing_bits). The NAL unit (codec1_nal_unit) for the first encodingmethod and the NAL unit (codec2_nal_unit) for the second encoding methodmay have the same configuration or different configurations. The NALunit for the first encoding method and the NAL unit for the secondencoding method may have different sizes.

Data encoded in the first encoding method is stored in a NAL unit forthe first encoding method. Data encoded in the second encoding method isstored in a NAL unit for the second encoding method.

In the NAL unit header (codec1_nal_unit_header, codec2_nal_unit_header),the NAL unit type (codec1_nal_unit_type, codec2_nal_unit_type) isstored. The NAL unit type is independent for each codec, and the type isdefined for each codec. That is, in a NAL unit for the first encodingmethod, a NAL unit type defined for the first encoding method isdescribed. In a NAL unit for the second encoding method, a NAL unit typedefined for the second encoding method is described.

According to this scheme, the first encoding method and the secondencoding method can be handled as different codecs.

Next, an encoding process according to this embodiment will bedescribed. FIG. 29 is a flowchart showing an encoding process accordingto this embodiment. The process in the drawing is a process performed byfirst encoder 4630 or second encoder 4650 defined as described above.The process in the drawing is mainly performed by multiplexer 4634 shownin FIG. 6 or multiplexer 4656 shown in FIG. 10.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod, and it is supposed that which PCC codec is used for the encodingis known. For example, a user, an external device or the like mayspecify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, thefirst encoding method or the second encoding method (S4631).

When the codec used is the second encoding method (if “second encodingmethod” in S4632), encoder 4613 generates a NAL unit in the NAL unitformat for the second encoding method (S4633). Encoder 4613 then setscodec2_nal_unit_type in the NAL unit header to the identifier of the NALunit for the second encoding method (S4634). In this way, encoder 4613generates a NAL unit having the set NAL unit header and including theencoded data in the payload. Encoder 4613 transmits the generated NALunit (S4635).

On the other hand, when the codec used is the first encoding method (if“first encoding method” in S4632), encoder 4613 generates a NAL unit inthe NAL unit format for the first encoding method (S4636). Encoder 4613then sets codec1_nal_unit_type in the NAL unit header to the identifierof the NAL unit for the first encoding method (S4637). In this way,encoder 4613 generates a NAL unit having the set NAL unit header andincluding the encoded data in the payload. Encoder 4613 then transmitsthe generated NAL unit (S4635).

Next, a decoding process according to this embodiment will be described.FIG. 30 is a flowchart showing a decoding process according to thisembodiment. The process in the drawing is a process performed by firstdecoder 4640 or second decoder 4660 defined as described above. In thefollowing, first decoder 4640 and second decoder 4660 may not bediscriminated, and the decoder may be referred to as decoder 4624. Theprocess in the drawing is mainly performed by demultiplexer 4641 shownin FIG. 8 or demultiplexer 4661 shown in FIG. 12.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod, and it is supposed that which PCC codec is used for the encodingis known. For example, information indicating the codec used is includedin the transmission signal, the multiplexed data, or the encoded data,and decoder 4624 determines the codec used by referring to theinformation. Note that decoder 4624 may determine the codec used basedon a signal obtained separately from these signals.

When the codec used is the second encoding method (if “second encodingmethod” in S4641), decoder 4624 receives a NAL unit in the format forthe second encoding method (S4642). Decoder 4624 then identifies thedata using the NAL unit format for the second encoding method andcodec2_nal_unit_type for the second encoding method based on thedetermination that the NAL unit is for the second encoding method(S4643). Decoder 4624 then decodes the PCC data in a decoding processfor the second encoding method (S4644).

On the other hand, when the codec used is the first encoding method (if“first encoding method” in S4641), decoder 4624 receives a NAL unit inthe format for the first encoding method (S4645). Decoder 4624 thenidentifies the data using the NAL unit format for the first encodingmethod and codec1_nal_unit_type for the first encoding method based onthe determination that the NAL unit is for the first encoding method(S4646). Decoder 4624 then decodes the PCC data in a decoding processfor the first encoding method (S4647).

Embodiment 3

In Embodiment 3, another way of defining a NAL unit will be described.In this embodiment, for a NAL unit, a format that is common to PCCcodecs is defined. Furthermore, an identifier of the common PCC codecNAL unit is defined.

FIG. 31 is a diagram showing a protocol stack in this case. FIGS. 32 to34 are diagrams showing an example of a common codec NAL unit format.FIG. 32 is a diagram showing a syntax example of a common PCC NAL unit.FIG. 33 is a diagram showing a syntax example of a common PCC NAL unitheader. FIG. 34 is a diagram showing a semantics example ofpcc_codec_type.

As a NAL unit format, a NAL unit format that is common to the PCC codecsis defined. A NAL unit (pcc_nal_unit) includes a header(pcc_nal_unit_header), a payload (pcc_nal_unit_payload), and a trailingbit (trailing_bits). Regardless of the codec, that is, whether data isto be stored in the first encoding method or the second encoding method,the same format is used.

In the NAL unit header (pcc_nal_unit_header), a NAL unit type(pcc_nal_unit_type) is stored. The NAL unit type is common to thecodecs, and a type common to the codecs is defined. That is, a commonNAL unit type defined is described for both a NAL unit for the firstencoding method and a NAL unit for the second encoding method. In theexample shown in FIG. 34, for example, PCC DataA is encoded data incodec 1, PCC DataB is encoded data in codec 2, PCC MetaDataA isadditional information in codec 1, and PCC MetaDataB is additionalinformation in codec 2.

According to this scheme, the first encoding method and the secondencoding method can be handled as the same codec.

Next, an encoding process according to this embodiment will bedescribed. FIG. 35 is a flowchart showing an encoding process accordingto this embodiment. The process in the drawing is a process performed byfirst encoder 4630 or second encoder 4650 defined as described above.The process in the drawing is mainly performed by multiplexer 4634 shownin FIG. 6 or multiplexer 4656 shown in FIG. 10.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod, and it is supposed that which PCC codec is used for the encodingis known. For example, a user, an external device or the like mayspecify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, thefirst encoding method or the second encoding method (S4651). Encoder4613 then generates a NAL unit in the common PCC NAL unit format(S4652).

Encoder 4613 then sets pcc_nal_unit_type in the NAL unit header to theidentifier of the common PCC NAL unit (S4653). Encoder 4613 thentransmits the NAL unit having the set NAL unit header and including theencoded data in the payload (S4654).

Next, a decoding process according to this embodiment will be described.FIG. 36 is a flowchart showing a decoding process according to thisembodiment. The process in the drawing is a process performed by firstdecoder 4640 or second decoder 4660 defined as described above. Theprocess in the drawing is mainly performed by demultiplexer 4641 shownin FIG. 8 or demultiplexer 4661 shown in FIG. 12.

Note that the process in the drawing is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod.

First, decoder 4624 determines the codec used for the encoding of thedata included in the NAL unit (S4661). For example, decoder 4624determines the codec used by referring to pcc_nal_unit_type in the NALunit header.

When the codec used is the second encoding method (if “second encodingmethod” in S4661), decoder 4624 receives a NAL unit in the common PCCformat (S4662). Decoder 4624 then identifies the data using the commonNAL unit format and the common pcc_nal_unit_type based on thedetermination that the NAL unit is a common NAL unit (S4663). Decoder4624 then decodes the PCC data in a decoding process for the secondencoding method (S4664).

On the other hand, when the codec used is the first encoding method (if“first encoding method” in S4661), decoder 4624 receives a NAL unit inthe common PCC format (S4665). Decoder 4624 then identifies the datausing the common NAL unit format and the common pcc_nal_unit_type basedon the determination that the NAL unit is a common NAL unit (S4666).Decoder 4624 then decodes the PCC data in a decoding process for thefirst encoding method (S4667).

In the following, variations of Embodiments 1 to 3 described above willbe described. As another method for indicating the PCC codec type, anyof the following methods can also be used.

In Embodiment 1, Embodiment 2, and Embodiment 3, cases where there aretwo codecs, that is, the first encoding method and the second encodingmethod, have been described. However, the methods described above can beapplied to cases where there are three or more PCC codecs.

In Embodiment 1 and Embodiment 3, identification information for the PCCcodec (pcc_codec_type in Embodiment 1 or pcc_nal_unit_type in Embodiment3) is described in the NAL unit header. However, the identificationinformation for the codec may be stored at another location.

The first encoding method and the second encoding method are not limitedto the examples described above and can be any codec. For example, thefirst encoding method and the second encoding method may be a pluralityof codecs resulting from fragmentation of GPCC or a plurality of codecsresulting from fragmentation of VPCC. For example, both the firstencoding method and the second encoding method may be VPCC, butdifferent video encoding schemes may be used in the first encodingmethod and the second encoding method. The video encoding scheme may beAVC or HEVC, for example. One or both of the first encoding method andthe second encoding method may be an encoding method including anotherencoding scheme for a video, an audio, a text application, or the like.

For example, the identification information for the codec may beincluded in the control information (signaling information) included inthe PCC-encoded stream. Here, the control information is metadata or thelike, such as a parameter set or supplemental enhancement information(SEI).

FIG. 37 is a flowchart of an encoding process by encoder 4613 in thiscase. First, encoder 4613 encodes PCC data (S4671), and describes theidentification information for the PCC codec at a predetermined location(parameter set, for example) in the encoded data (S4672). Encoder 4613then generates a NAL unit including the encoded data, and transmits thegenerated NAL unit (S4673).

The identification information for the PCC codec may be defined asprofile, and indicated by metadata. When the same codec is used for thewhole of a sequence, a sequence parameter set may include theidentification information for the PCC codec. When a different codec isused for encoding of each PCC frame, a parameter set that describesinformation on each frame may include the identification information forthe PCC codec. For example, when a different codec is used for eachpiece of PCC data, such as when different codecs are used for thegeometry information and the attribute information, a parameter set thatdescribes information on each piece of data may include theidentification information for the PCC codec. That is, informationindicating the codec for the geometry information may be included incontrol information (a parameter set or the like) for the geometryinformation, and information indicating the codec for the attributeinformation may be included in control information (a parameter set orthe like) for the attribute information.

Note that the identification information for the codec may be stored atany of the locations described above or may be stored at a plurality oflocations. For example, the identification information for the codec maybe stored in both the encoded stream and the NAL unit header. When theidentification information for the codec is stored at a plurality oflocations, the same information may be stored at the plurality oflocations, or different information may be stored at the plurality oflocations. The “different information” are information indicating GPCCor VPCC and information indicating any of a plurality of codecsresulting from fragmentation of GPCC or VPCC.

When a NAL unit includes a parameter set, demultiplexer 4641 or 4661included in decoder 4624 can determine whether the data included in thepayload of the NAL unit is data encoded in the first encoding method ordata encoded in the second encoding method by analyzing what isdescribed in the parameter set. Therefore, decoder 4624 can quicklyfilter a NAL unit that is not required for decoding.

FIG. 38 is a flowchart of a decoding process by decoder 4624 in thiscase. First, decoder 4624 receives a NAL unit (S4675), and identifies apredetermined data that describes the identification information for thePCC codec (the parameter set described above, for example) usingpec_nal_unit_type in the NAL unit header (S4676). Decoder 4624 thenidentifies the PCC codec indicated in the predetermined data byanalyzing predetermined data (the parameter set, for example) (S4677).Decoder 4624 then decodes the encoded data using the identified PCCcodec (S4678).

Although an example in which the encoded stream is stored in a NAL unithas been shown above, any unit according to a predetermined scheme canbe used instead of the NAL unit.

Embodiment 4

In Embodiment 4, encoder 4670 having the functions of both first encoder4630 and second encoder 4650 described above and decoder 4680 having thefunctions of both first decoder 4640 and second decoder 4660 describedabove will be described.

FIG. 39 is a block diagram showing encoder 4670 according to thisembodiment. Encoder 4670 includes first encoder 4630 and second encoder4650 described above and multiplexer 4671. Multiplexer 4671 multiplexesencoded data generated by first encoder 4630 and encoded data generatedby second encoder 4650, and outputs the resulting encoded data.

FIG. 40 is a block diagram showing decoder 4680 according to thisembodiment. Decoder 4680 includes first decoder 4640 and second decoder4660 described above and demultiplexer 4681. Demultiplexer 4681 extractsencoded data generated using the first encoding method and encoded datagenerated using second encoding method from the input encoded data.Demultiplexer 4681 outputs the encoded data generated using the firstencoding method to first decoder 4640, and outputs the encoded datagenerated using the second encoding method to second decoder 4660.

With the configuration described above, encoder 4670 can encode pointcloud data by selectively using the first encoding method or the secondencoding method. Decoder 4680 can decode encoded data encoded using thefirst encoding method, encoded data using the second encoding method,and encoded data encoded using both the first encoding method and thesecond encoding method.

For example, encoder 4670 may change the encoding method (between thefirst encoding method and the second encoding method) on apoint-cloud-data basis or on a frame basis. Alternatively encoder 4670may change the encoding method on the basis of an encodable unit.

For example, encoder 4670 generates encoded data (encoded stream)including the identification information for the PCC codec describedabove with regard to Embodiment 1 or Embodiment 3.

Demultiplexer 4681 in decoder 4680 identifies data using theidentification information for the PCC codec described above with regardto Embodiment 1 or Embodiment 3, for example. When the data is dataencoded in the first encoding method, demultiplexer 4681 outputs thedata to first decoder 4640. When the data is data encoded in the secondencoding method, demultiplexer 4681 outputs the data to second decoder4660.

Encoder 4670 may transmit, as the control information (signalinginformation), information indicating whether both the encoding methodsare used or any one of the encoding methods is used, in addition to theidentification information for the PCC codec.

Next, an encoding process according to this embodiment will bedescribed. FIG. 41 is a flowchart showing an encoding process accordingto this embodiment. Using the identification information for the PCCcodec described above with regard to Embodiment 1, Embodiment 2,Embodiment 3, and variations thereof allows an encoding process readyfor a plurality of codecs. Note that although FIG. 41 shows an examplein which the scheme according to Embodiment 1 is used, the same processcan be applied to the other schemes.

First, encoder 4670 encodes PCC data in both or one of the codecs, thatis, the first encoding method and the second encoding method (S4681).

When the codec used is the second encoding method (if “second encodingmethod” in S4682), encoder 4670 sets pcc_codec_type in the NAL unitheader to a value that indicates that data included in the payload ofthe NAL unit is data encoded in the second encoding method (S4683).Encoder 4670 then sets pcc_nal_unit_type in the NAL unit header to theidentifier of the NAL unit for the second encoding method (S4684).Encoder 4670 then generates a NAL unit having the set NAL unit headerand including the encoded data in the payload. Encoder 4670 thentransmits the generated NAL unit (S4685).

On the other hand, when the codec used is the first encoding method (if“first encoding method” in S4682), encoder 4670 sets pcc_codec_type inthe NAL unit header to a value that indicates that data included in thepayload of the NAL unit is data encoded in the first encoding method(S4686). Encoder 4670 then sets pcc_nal_unit_type in the NAL unit headerto the identifier of the NAL unit for the first encoding method (S4687).Encoder 4670 then generates a NAL unit having the set NAL unit headerand including the encoded data in the payload. Encoder 4670 thentransmits the generated NAL unit (S4685).

Next, a decoding process according to this embodiment will be described.FIG. 42 is a flowchart showing a decoding process according to thisembodiment. Using the identification information for the PCC codecdescribed above with regard to Embodiment 1, Embodiment 2, Embodiment 3,and variations thereof allows a decoding process ready for a pluralityof codecs. Note that although FIG. 42 shows an example in which thescheme according to Embodiment 1 is used, the same process can beapplied to the other schemes.

First, decoder 4680 receives a NAL unit (S4691). For example, the NALunit is the NAL unit generated in the process by encoder 4670 describedabove.

Decoder 4680 then determines whether pcc_codec_type in the NAL unitheader indicates the first encoding method or the second encoding method(S4692).

When pcc_codec_type indicates the second encoding method (if “secondencoding method” in S4692), decoder 4680 determines that the dataincluded in the payload of the NAL unit is data encoded in the secondencoding method (S4693). Decoder 4680 then identifies the data based onthe determination that pcc_nal_unit_type in the NAL unit header is theidentifier of the NAL unit for the second encoding method (S4694).Decoder 4680 then decodes the PCC data in a decoding process for thesecond encoding method (S4695).

On the other hand, when pcc_codec_type indicates the first encodingmethod (if “first encoding method” in S4692), decoder 4680 determinesthat the data included in the payload of the NAL unit is data encoded inthe first encoding method (S4696). Decoder 4680 then identifies the databased on the determination that pcc_nal_unit_type in the NAL unit headeris the identifier of the NAL unit for the first encoding method (S4697).Decoder 4680 then decodes the PCC data in a decoding process for thefirst encoding method (S4698).

As described above, the three-dimensional data encoding device accordingto an aspect of the present disclosure generates an encoded stream byencoding three-dimensional data (point cloud data, for example) (inS4671 in FIG. 37, for example), and stores information indicating theencoding method used for the encoding among the first encoding methodand the second encoding method (identification information for thecodec, for example) in the control information (a parameter set, forexample) for the encoded stream (in S4672 in FIG. 37, for example).

With such a configuration, the three-dimensional data decoding devicecan determine the encoding method used for the encoding from theinformation stored in the control information, when decoding the encodedstream generated by the three-dimensional data encoding device.Therefore, the three-dimensional data decoding device can correctlydecode the encoded stream even when a plurality of encoding methods areused.

The three-dimensional data includes geometry information, for example.In the encoding described above, the three-dimensional data encodingdevice encodes the geometry information. In the storage described above,the three-dimensional data encoding device stores the informationindicating the encoding method used for the encoding of the geometryinformation among the first encoding method and the second encodingmethod in the control information for the geometry information.

The three-dimensional data includes geometry information and attributeinformation, for example. In the encoding described above, thethree-dimensional data encoding device encodes the geometry informationand the attribute information. In the storage described above, thethree-dimensional data encoding device stores the information indicatingthe encoding method used for the encoding of the geometry informationamong the first encoding method and the second encoding method in thecontrol information for the geometry information, and stores theinformation indicating the encoding method used for the encoding of theattribute information among the first encoding method and the secondencoding method in the control information for the attributeinformation.

With such a configuration, different encoding methods can be used forthe geometry information and the attribute information, and therefore,the coding efficiency can be improved.

For example, the three-dimensional data encoding method further includesstoring the encoded stream in one or more units (NAL units, for example)(in S4673 in FIG. 37, for example).

For example, as described above with reference to FIGS. 15 to 18illustrating Embodiment 1, the unit includes information(pcc_nal_unit_type, for example) indicating the type of data included inthe unit that has a format that is common to the first encoding methodand the second encoding method and is independently defined for thefirst encoding method and the second encoding method.

For example, as described above with reference to FIGS. 23 to 28illustrating Embodiment 2, the unit includes information(codec1_nal_unit_type or codec2_nal_unit_type, for example) indicatingthe type of data included in the unit that has different formats for thefirst encoding method and the second encoding method and isindependently defined for the first encoding method and the secondencoding method.

For example, as described above with reference to FIGS. 32 to 34illustrating Embodiment 3, the unit includes information(pcc_nal_unit_type, for example) indicating the type of data included inthe unit that has a format that is common to the first encoding methodand the second encoding method and is commonly defined for the firstencoding method and the second encoding method.

For example, the three-dimensional data encoding device includes aprocessor and a memory and the processor performs the processesdescribed above using the memory.

The three-dimensional data decoding device according to this embodimentdetermines the encoding method used for encoding of an encoded streamgenerated by encoding of three-dimensional data based on the informationindicating the encoding method used for the encoding of thethree-dimensional data among the first encoding method and the secondencoding method (identification information for the codec, for example)included in the control information (a parameter set, for example) forthe encoded stream (in S4677 in FIG. 38, for example), and decodes theencoded stream using the determined encoding method (in S4678 in FIG.38, for example).

With such a configuration, the three-dimensional data decoding devicecan determine the encoding method used for the encoding from theinformation stored in the control information, when decoding the encodedstream. Therefore, the three-dimensional data decoding device cancorrectly decode the encoded stream even when a plurality of encodingmethods are used.

The three-dimensional data includes geometry information, and theencoded stream includes encoded data of the geometry information, forexample. In the determination described above, the three-dimensionaldata decoding device determines the encoding method used for theencoding of the geometry information based on the information indicatingthe encoding method used for the encoding of the geometry informationamong the first encoding method and the second encoding method includedin the control information for the geometry information included in theencoded stream. In the decoding described above, the three-dimensionaldata decoding device decodes the encoded data of the geometryinformation using the determined encoding method used for the encodingof the geometry information.

The three-dimensional data includes geometry information and attributeinformation, and the encoded stream includes encoded data of thegeometry information and encoded data of the attribute information, forexample. In the determination described above, the three-dimensionaldata decoding device determines the encoding method used for theencoding of the geometry information based on the information indicatingthe encoding method used for the encoding of the geometry informationamong the first encoding method and the second encoding method includedin the control information for the geometry information included in theencoded stream, and determines the encoding method used for the encodingof the attribute information based on the information indicating theencoding method used for the encoding of the attribute information amongthe first encoding method and the second encoding method included in thecontrol information for the attribute information included in theencoded stream. In the decoding described above, the three-dimensionaldata decoding device decodes the encoded data of the geometryinformation using the determined encoding method used for the encodingof the geometry information, and decodes the encoded data of theattribute information using the determined encoding method used for theencoding of the attribute information.

With such a configuration, different encoding methods can be used forthe geometry information and the attribute information, and therefore,the coding efficiency can be improved.

For example, the encoded stream is stored in one or more units (NALunits, for example), and the three-dimensional data decoding devicefurther obtains the encoded stream from the one or more units.

For example, as described above with reference to FIGS. 15 to 18illustrating Embodiment 1, the unit includes information(pcc_nal_unit_type, for example) indicating the type of data included inthe unit that has a format that is common to the first encoding methodand the second encoding method and is independently defined for thefirst encoding method and the second encoding method.

For example, as described above with reference to FIGS. 23 to 28illustrating Embodiment 2, the unit includes information(codec1_nal_unit_type or codec2_nal_unit_type, for example) indicatingthe type of data included in the unit that has different formats for thefirst encoding method and the second encoding method and isindependently defined for the first encoding method and the secondencoding method.

For example, as described above with reference to FIGS. 32 to 34illustrating Embodiment 3, the unit includes information(pcc_nal_unit_type, for example) indicating the type of data included inthe unit that has a format that is common to the first encoding methodand the second encoding method and is commonly defined for the firstencoding method and the second encoding method.

For example, the three-dimensional data decoding device includes aprocessor and a memory and the processor performs the processesdescribed above using the memory.

Embodiment 5

In Embodiment 5, a method of storing the NAL unit described above withregard to Embodiment 1 in an ISOBMFF file will be described.

ISOBMFF is a file format standard prescribed in ISO/IEC14496-12. ISOBMFFis a standard that does not depend on any medium, and prescribes aformat that allows various media, such as a video, an audio, and a text,to be multiplexed and stored.

A basic structure (file) of ISOBMFF will be described. A basic unit ofISOBMFF is a box. A box is formed by type, length, and data, and a fileis a set of various types of boxes.

FIG. 43 is a diagram showing a basic structure (file) of ISOBMFF. A filein ISOBMFF includes boxes, such as ftyp that indicates the brand of thefile by four-character code (4CC), moov that stores metadata, such ascontrol information (signaling information), and mdat that stores data.

A method for storing each medium in the ISOBMFF file is separatelyprescribed. For example, a method of storing an AVC video or an HEVCvideo is prescribed in ISO/IEC14496-15. Here, it can be contemplated toexpand the functionality of ISOBMFF and use ISOBMFF to accumulate ortransmit PCC-encoded data. However, there has been no convention forstoring PCC-encoded data in an ISOBMFF file. In this embodiment, amethod of storing PCC-encoded data in an ISOBMFF file will be described.

FIG. 44 is a diagram showing a protocol stack in a case where a commonPCC codec NAL unit in an ISOBMFF file. Here, the common PCC codec NALunit described above with regard to Embodiment 1 is stored in an ISOBMFFfile. Although the NAL unit is common to PCC codecs, a storage methodfor each codec (Carriage of Codec1, Carriage of Codec2) is desirablyprescribed, since a plurality of PCC codecs are stored in the NAL unit.

Next, a method of storing a common PCC NAL unit that supports aplurality of PCC codecs in an ISOBMFF file will be described. FIG. 45 isa diagram showing an example in which a common PCC NAL unit is stored inan ISOBMFF file for the storage method for codec 1 (Carriage of Codec).FIG. 46 is a diagram showing an example in which a common PCC NAL unitis stored in an ISOBMFF file for the storage method for codec 2(Carriage of Codec2).

Here, ftyp is information that is important for identification of thefile format, and a different identifier of ftyp is defined for eachcodec. When PCC-encoded data encoded in the first encoding method(encoding scheme) is stored in the file, ftyp is set to pcc1. WhenPCC-encoded data encoded in the second encoding method is stored in thefile, ftyp is set to pcc2.

Here, pcc1 indicates that PCC codec 1 (first encoding method) is used.pcc2 indicates that PCC codec2 (second encoding method) is used. Thatis, pcc1 and pcc2 indicate that the data is PCC (encodedthree-dimensional data (point cloud data)), and indicate the PCC codec(first encoding method or second encoding method).

In the following, a method of storing a NAL unit in an ISOBMFF file willbe described. The multiplexer analyzes the NAL unit header, anddescribes pcc1 in ftyp of ISOBMFF if pcc_codec_type=Codec1.

The multiplexer analyzes the NAL unit header, and describes pcc2 in ftypof ISOBMFF if pcc_codec_type=Codec2.

If pcc_nal_unit_type is metadata, the multiplexer stores the NAL unit inmoov or mdat in a predetermined manner, for example. Ifpcc_nal_unit_type is data, the multiplexer stores the NAL unit in moovor mdat in a predetermined manner, for example.

For example, the multiplexer may store the NAL unit size in the NALunit, as with HEVC.

According to this storage method, the demultiplexer (a system layer) candetermine whether the PCC-encoded data is encoded in the first encodingmethod or the second encoding method by analyzing ftyp included in thefile. Furthermore, as described above, by determining whether thePCC-encoded data is encoded in the first encoding method or the secondencoding method, the encoded data encoded in any one of the encodingmethods can be extracted from the data including both the encoded dataencoded in the encoding methods. Therefore, when transmitting theencoded data, the amount of data transmitted can be reduced. Inaddition, according to this storage method, different data (file)formats do not need to be set for the first encoding method and thesecond encoding method, and a common data format can be used for thefirst encoding method and the second encoding method.

Note that, when the identification information for the codec, such asftyp of ISOBMFF, is indicated in the metadata of the system layer, themultiplexer can store a NAL unit without pcc_nal_unit_type in theISOBMFF file.

Next, configurations and operations of the multiplexer of thethree-dimensional data encoding system (three-dimensional data encodingdevice) according to this embodiment and the demultiplexer of thethree-dimensional data decoding system (three-dimensional data decodingdevice) according to this embodiment will be described.

FIG. 47 is a diagram showing a configuration of first multiplexer 4710.First multiplexer 4710 includes file converter 4711 that generatesmultiplexed data (file) by storing encoded data generated by firstencoder 4630 and control information (NAL unit) in an ISOBMFF file.First multiplexer 4710 is included in multiplexer 4614 shown in FIG. 1,for example.

FIG. 48 is a diagram showing a configuration of first demultiplexer4720. First demultiplexer 4720 includes file inverse converter 4721 thatobtains encoded data and control information (NAL unit) from multiplexeddata (file) and outputs the obtained encoded data and controlinformation to first decoder 4640. First demultiplexer 4720 is includedin demultiplexer 4623 shown in FIG. 1, for example.

FIG. 49 is a diagram showing a configuration of second multiplexer 4730.Second multiplexer 4730 includes file converter 4731 that generatesmultiplexed data (file) by storing encoded data generated by secondencoder 4650 and control information (NAL unit) in an ISOBMFF file.Second multiplexer 4730 is included in multiplexer 4614 shown in FIG. 1,for example.

FIG. 50 is a diagram showing a configuration of second demultiplexer4740. Second demultiplexer 4740 includes file inverse converter 4741that obtains encoded data and control information (NAL unit) frommultiplexed data (file) and outputs the obtained encoded data andcontrol information to second decoder 4660. Second demultiplexer 4740 isincluded in demultiplexer 4623 shown in FIG. 1, for example.

FIG. 51 is a flowchart showing a multiplexing process by firstmultiplexer 4710. First, first multiplexer 4710 analyzes pcc_codec_typein the NAL unit header, thereby determining whether the codec used isthe first encoding method or the second encoding method (S4701).

When pcc_codec_type represents the second encoding method (if “secondencoding method” in S4702), first multiplexer 4710 does not process theNAL unit (S4703).

On the other hand, when pcc_codec_type represents the first encodingmethod (if “first encoding method” in S4702), first multiplexer 4710describes pcc1 in ftyp (S4704). That is, first multiplexer 4710describes information indicating that data encoded in the first encodingmethod is stored in the file in ftyp.

First multiplexer 4710 then analyzes pcc_nal_unit_type in the NAL unitheader, and stores the data in a box (moov or mdat, for example) in apredetermined manner suitable for the data type represented bypcc_nal_unit_type (S4705). First multiplexer 4710 then creates anISOBMFF file including the ftyp described above and the box describedabove (S4706).

FIG. 52 is a flowchart showing a multiplexing process by secondmultiplexer 4730. First, second multiplexer 4730 analyzes pcc_codec_typein the NAL unit header, thereby determining whether the codec used isthe first encoding method or the second encoding method (S4711).

When pcc_codec_type represents the second encoding method (if “secondencoding method” in S4712), second multiplexer 4730 describes pcc2 inftyp (S4713). That is, second multiplexer 4730 describes informationindicating that data encoded in the second encoding method is stored inthe file in ftyp.

Second multiplexer 4730 then analyzes pcc_nal_unit_type in the NAL unitheader, and stores the data in a box (moov or mdat, for example) in apredetermined manner suitable for the data type represented bypcc_nal_unit_type (S4714). Second multiplexer 4730 then creates anISOBMFF file including the ftyp described above and the box describedabove (S4715).

On the other hand, when pcc_codec_type represents the first encodingmethod (if “first encoding method” in S4712), second multiplexer 4730does not process the NAL unit (S4716).

Note that the process described above is an example in which PCC data isencoded in any one of the first encoding method and the second encodingmethod. First multiplexer 4710 and second multiplexer 4730 store adesired NAL unit in a file by identifying the codec type of the NALunit. Note that, when the identification information for the PCC codecis included in a location other than the NAL unit header, firstmultiplexer 4710 and second multiplexer 4730 may identify the codec type(first encoding method or second encoding method) based on theidentification information for the PCC codec included in the locationother than the NAL unit header in step S4701 or S4711.

When storing data in a file in step S4706 or S4714, first multiplexer4710 and second multiplexer 4730 may store the data in the file afterdeleting pec_nal_unit_type from the NAL unit header.

FIG. 53 is a flowchart showing a process performed by firstdemultiplexer 4720 and first decoder 4640. First, first demultiplexer4720 analyzes ftyp in an ISOBMFF file (S4721). When the codecrepresented by ftyp is the second encoding method (pcc2) (if “secondencoding method” in S4722), first demultiplexer 4720 determines that thedata included in the payload of the NAL unit is data encoded in thesecond encoding method (S4723). First demultiplexer 4720 also transmitsthe result of the determination to first decoder 4640. First decoder4640 does not process the NAL unit (S4724).

On the other hand, when the codec represented by ftyp is the firstencoding method (pcc1) (if “first encoding method” in S4722), firstdemultiplexer 4720 determines that the data included in the payload ofthe NAL unit is data encoded in the first encoding method (S4725). Firstdemultiplexer 4720 also transmits the result of the determination tofirst decoder 4640.

First decoder 4640 identifies the data based on the determination thatpcc_nal_unit_type in the NAL unit header is the identifier of the NALunit for the first encoding method (S4726). First decoder 4640 thendecodes the PCC data using a decoding process for the first encodingmethod (S4727).

FIG. 54 is a flowchart showing a process performed by seconddemultiplexer 4740 and second decoder 4660. First, second demultiplexer4740 analyzes ftyp in an ISOBMFF file (S4731). When the codecrepresented by ftyp is the second encoding method (pcc2) (if “secondencoding method” in S4732), second demultiplexer 4740 determines thatthe data included in the payload of the NAL unit is data encoded in thesecond encoding method (S4733). Second demultiplexer 4740 also transmitsthe result of the determination to second decoder 4660.

Second decoder 4660 identifies the data based on the determination thatpcc_nal_unit_type in the NAL unit header is the identifier of the NALunit for the second encoding method (S4734). Second decoder 4660 thendecodes the PCC data using a decoding process for the second encodingmethod (S4735).

On the other hand, when the codec represented by ftyp is the firstencoding method (pcc1) (if “first encoding method” in S4732), seconddemultiplexer 4740 determines that the data included in the payload ofthe NAL unit is data encoded in the first encoding method (S4736).Second demultiplexer 4740 also transmits the result of the determinationto second decoder 4660. Second decoder 4660 does not process the NALunit (S4737).

As described above, for example, since the codec type of the NAL unit isidentified in first demultiplexer 4720 or second demultiplexer 4740, thecodec type can be identified in an early stage. Furthermore, a desiredNAL unit can be input to first decoder 4640 or second decoder 4660, andan unwanted NAL unit can be removed. In this case, the process of firstdecoder 4640 or second decoder 4660 analyzing the identificationinformation for the codec may be unnecessary. Note that a process ofreferring to the NAL unit type again and analyzing the identificationinformation for the codec may be performed by first decoder 4640 orsecond decoder 4660.

Furthermore, if pcc_nal_unit_type is deleted from the NAL unit header byfirst multiplexer 4710 or second multiplexer 4730, first demultiplexer4720 or second demultiplexer 4740 can output the NAL unit to firstdecoder 4640 or second decoder 4660 after adding pcc_nal_unit_type tothe NAL unit.

Embodiment 6

In Embodiment 6, a multiplexer and a demultiplexer that correspond toencoder 4670 and decoder 4680 ready for a plurality of codecs describedabove with regard to Embodiment 4 will be described. FIG. 55 is adiagram showing configurations of encoder 4670 and third multiplexer4750 according to this embodiment.

Encoder 4670 encodes point cloud data in both or one of the firstencoding method and the second encoding method. Encoder 4670 may changethe encoding method (between the first encoding method and the secondencoding method) on a point-cloud-data basis or on a frame basis.Alternatively encoder 4670 may change the encoding method on the basisof an encodable unit.

Encoder 4670 generates encoded data (encoded stream) including theidentification information for the PCC codec described above with regardto Embodiments 1 to 4.

Third multiplexer 4750 includes file converter 4751. File converter 4751converts a NAL unit output from encoder 4670 into a PCC data file. Fileconverter 4751 analyzes the codec identification information included inthe NAL unit header, and determines whether the PCC-encoded data is dataencoded in the first encoding method, data encoded in the secondencoding method, or data encoded in both the encoding methods. Fileconverter 4751 describes a brand name that allows codec identificationin ftyp. For example, when indicating the data is encoded in both theencoding methods, pcc3 is described in ftyp.

Note that, when encoder 4670 describes the PCC codec identificationinformation in a location other than the NAL unit, file converter 4751may determine the PCC codec (encoding method) based on theidentification information.

FIG. 56 is a diagram showing configurations of third demultiplexer 4760and decoder 4680 according to this embodiment.

Third demultiplexer 4760 includes file inverse converter 4761. Fileinverse converter 4761 analyzes ftyp included in a file, and determineswhether the PCC-encoded data is data encoded in the first encodingmethod, data encoded in the second encoding method, or data encoded inboth the encoding methods.

When the PCC-encoded data is data encoded in any one of the encodingmethods, the data is input to an appropriate one of first decoder 4640and second decoder 4660, and is not input to the other decoder. When thePCC-encoded data is data encoded in both the encoding methods, the datais input to decoder 4680 ready for both the encoding methods.

Decoder 4680 decodes the PCC-encoded data in both or one of the firstencoding method and the second encoding method.

FIG. 57 is a flowchart showing a process performed by third multiplexer4750 according to this embodiment.

First, third multiplexer 4750 analyzes pcc_codec_type in the NAL unitheader, thereby determining whether the codec(s) used is the firstencoding method, the second encoding method, or both the first encodingmethod and the second encoding method (S4741).

When the second encoding method is used (if Yes in S4742 and “secondencoding method” in S4743), third multiplexer 4750 describes pcc2 inftyp (S4744). That is, third multiplexer 4750 describes informationindicating that data encoded in the second encoding method is stored inthe file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unitheader, and stores the data in a box (moov or mdat, for example) in apredetermined manner suitable for the data type represented bypcc_nal_unit_type (S4745). Third multiplexer 4750 then creates anISOBMFF file including the ftyp described above and the box describedabove (S4746).

When the first encoding method is used (if Yes in S4742 and “firstencoding method” in S4743), third multiplexer 4750 describes pcc1 inftyp (S4747). That is, third multiplexer 4750 describes informationindicating that data encoded in the first encoding method is stored inthe file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unitheader, and stores the data in a box (moov or mdat, for example) in apredetermined manner suitable for the data type represented bypcc_nal_unit_type (S4748). Third multiplexer 4750 then creates anISOBMFF file including the ftyp described above and the box describedabove (S4746).

When both the first encoding method and the second encoding method areused (if No in S4742), third multiplexer 4750 describes pcc3 in ftyp(S4749). That is, third multiplexer 4750 describes informationindicating that data encoded in both the encoding methods is stored inthe file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unitheader, and stores the data in a box (moov or mdat, for example) in apredetermined manner suitable for the data type represented bypcc_nal_unit_type (S4750). Third multiplexer 4750 then creates anISOBMFF file including the ftyp described above and the box describedabove (S4746).

FIG. 58 is a flowchart showing a process performed by thirddemultiplexer 4760 and decoder 4680. First, third demultiplexer 4760analyzes ftyp included in an ISOBMFF file (S4761). When the codecrepresented by ftyp is the second encoding method (pcc2) (if Yes inS4762 and “second encoding method” in S4763), third demultiplexer 4760determines that the data included in the payload of the NAL unit is dataencoded in the second encoding method (S4764). Third demultiplexer 4760also transmits the result of the determination to decoder 4680.

Decoder 4680 identifies the data based on the determination thatpec_nal_unit_type in the NAL unit header is the identifier of the NALunit for the second encoding method (S4765). Decoder 4680 then decodesthe PCC data using a decoding process for the second encoding method(S4766).

When the codec represented by ftyp is the first encoding method (pcc1)(if Yes in S4762 and “first encoding method” in S4763), thirddemultiplexer 4760 determines that the data included in the payload ofthe NAL unit is data encoded in the first encoding method (S4767). Thirddemultiplexer 4760 also transmits the result of the determination todecoder 4680.

Decoder 4680 identifies the data based on the determination thatpcc_nal_unit_type in the NAL unit header is the identifier of the NALunit for the first encoding method (S4768). Decoder 4680 then decodesthe PCC data using a decoding process for the first encoding method(S4769).

When ftyp indicates that both the encoding methods are used (pcc3) (ifNo in S4762), third demultiplexer 4760 determines that the data includedin the payload of the NAL unit is data encoded in both the firstencoding method and the second encoding method (S4770). Thirddemultiplexer 4760 also transmits the result of the determination todecoder 4680.

Decoder 4680 identifies the data based on the determination thatpcc_nal_unit_type in the NAL unit header is the identifier of the NALunit for the codecs described in pcc_codec_type (S4771). Decoder 4680then decodes the PCC data using decoding processes for both the encodingmethods (S4772). That is, decoder 4680 decodes the data encoded in thefirst encoding method using a decoding process for the first encodingmethod, and decodes the data encoded in the second encoding method usinga decoding process for the second encoding method.

In the following, variations of this embodiment will be described. Astypes of brands represented by ftyp, the types described below can beindicated by the identification information. Furthermore, a combinationof a plurality of the types described below can also be indicated by theidentification information.

The identification information may indicate whether the original dataobject yet to be PCC-encoded is a point cloud whose range is limited ora large point cloud whose range is not limited, such as map information.

The identification information may indicate whether the original datayet to be PCC-encoded is a static object or a dynamic object.

As described above, the identification information may indicate whetherthe PCC-encoded data is data encoded in the first encoding method ordata encoded in the second encoding method.

The identification information may indicate an algorithm used in the PCCencoding. Here, the “algorithm” means an encoding method that can beused in the first encoding method or the second encoding method, forexample.

The identification information may indicate a differentiation betweenmethods of storing the PCC-encoded data into an ISOBMFF file. Forexample, the identification information may indicate whether the storagemethod used is a storage method for accumulation or a storage method forreal-time transmission, such as dynamic streaming.

Although the method of storing a NAL unit described in Embodiment 1 hasbeen described in Embodiment 5, and the method of storing a NAL unitdescribed in Embodiment 4 has been described in Embodiment 6, the samestorage methods can be applied to the NAL unit described in Embodiments2 and 3 to store the identification information for the PCC codec intoan ISOBMFF file.

Although an example in which ISOBMFF is used as a file format has beendescribed in Embodiments 5 and 6, other formats can also be used. Forexample, the method according to this embodiment can also be used whenPCC-encoded data is stored in MPEG-2 TS Systems, MPEG-DASH, MMT, or RMP.

Although an example in which metadata, such as the identificationinformation, is stored in ftyp has been shown above, metadata can alsobe stored in a location other than ftyp. For example, the metadata maybe stored in moov.

As described above, a three-dimensional data storing device (orthree-dimensional data multiplexing device or three-dimensional dataencoding device) performs the process shown in FIG. 59.

First, the three-dimensional data storing device (which includes firstmultiplexer 4710, second multiplexer 4730 or third multiplexer 4750, forexample) acquires one or more units (NAL units, for example) that storean encoded stream, which is encoded point cloud data (S4781). Thethree-dimensional data storing device then stores the one or more unitsin a file (an ISOBMFF file, for example) (S4782). In the storage(S4782), the three-dimensional data storing device also storesinformation indicating that the data stored in the file is encoded pointcloud data (pcc1, pcc2, or pcc3, for example) in the control information(ftyp, for example) (referred to also as signaling information) for thefile.

With such a configuration, a device that processes the file generated bythe three-dimensional data storing device can quickly determine whetherthe data stored in the file is encoded point cloud data or not byreferring to the control information for the file. Therefore, theprocessing amount of the device can be reduced, or the processing speedof the device can be increased.

For example, the information indicates the encoding method used for theencoding of the point cloud data among the first encoding method and thesecond encoding method. Note that the fact that the data stored in thefile is encoded point cloud data and the encoding method used for theencoding of the point cloud data among the first encoding method and thesecond encoding method may be indicated by a single piece of informationor different pieces of information.

With such a configuration, a device that processes the file generated bythe three-dimensional data storing device can quickly determine thecodec used for the data stored in the file by referring to the controlinformation for the file. Therefore, the processing amount of the devicecan be reduced, or the processing speed of the device can be increased.

For example, the first encoding method is a method (GPCC) that encodesgeometry information that represents the position of point cloud data asan N-ary tree (N represents an integer equal to or greater than 2) andencodes attribute information using the geometry information, and thesecond encoding method is a method (VPCC) that generates atwo-dimensional image from point cloud data and encodes thetwo-dimensional image in a video encoding method.

For example, the file described above is in conformity with ISOBMFF(ISO-based media file format).

For example, the three-dimensional data storing device includes aprocessor and a memory and the processor performs the processesdescribed above using the memory.

As described above, a three-dimensional data acquisition device (orthree-dimensional data demultiplexing device or three-dimensional datadecoding device) performs the process shown in FIG. 60.

The three-dimensional data acquisition device (which includes firstdemultiplexer 4720, second demultiplexer 4740, or third demultiplexer4760, for example) acquires a file (an ISOBMFF file, for example) thatstores one or more units (NAL units, for example) that store an encodedstream, which is encoded point cloud data (S4791). The three-dimensionaldata acquisition device acquires the one or more units from the file(S4792). The control information (ftyp, for example) for the fileincludes information indicating that the data stored in the file isencoded point cloud data (pcc1, pcc2, or pcc3, for example).

For example, the three-dimensional data acquisition device determineswhether the data stored in the file is encoded point cloud data or notby referring to the information. When the three-dimensional dataacquisition device determines that the data stored in the file isencoded point cloud data, the three-dimensional data acquisition devicegenerates point cloud data by decoding the encoded point cloud dataincluded in the one or more units. Alternatively when thethree-dimensional data acquisition device determines that the datastored in the file is encoded point cloud data, the three-dimensionaldata acquisition device outputs information indicating that the dataincluded in the one or more units is encoded point cloud data to aprocessor in a subsequent stage (first decoder 4640, second decoder4660, or decoder 4680, for example) (or notifies a processor in asubsequent stage that the data included in the one or more units isencoded point cloud data).

With such a configuration, the three-dimensional data acquisition devicecan quickly determine whether the data stored in the file is encodedpoint cloud data or not by referring to the control information for thefile. Therefore, the processing amount of the three-dimensional dataacquisition device or a device in a subsequent stage can be reduced, orthe processing speed of the three-dimensional data acquisition device ora device in a subsequent stage can be increased.

For example, the information represents the encoding method used for theencoding among the first encoding method and the second encoding method.Note that the fact that the data stored in the file is encoded pointcloud data and the encoding method used for the encoding of the pointcloud data among the first encoding method and the second encodingmethod may be indicated by a single piece of information or differentpieces of information.

With such a configuration, the three-dimensional data acquisition devicecan quickly determine the codec used for the data stored in the file byreferring to the control information for the file. Therefore, theprocessing amount of the three-dimensional data acquisition device or adevice in a subsequent stage can be reduced, or the processing speed ofthe three-dimensional data acquisition device or a device in asubsequent stage can be increased.

For example, based on the information, the three-dimensional dataacquisition device acquires the data encoded in any one of the firstencoding method and the second encoding method from the encoded pointcloud data including the data encoded in the first encoding method andthe data encoded in the second encoding method.

For example, the first encoding method is a method (GPCC) that encodesgeometry information that represents the position of point cloud data asan N-ary tree (N represents an integer equal to or greater than 2) andencodes attribute information using the geometry information, and thesecond encoding method is a method (VPCC) that generates atwo-dimensional image from point cloud data and encodes thetwo-dimensional image in a video encoding method.

For example, the file described above is in conformity with ISOBMFF(ISO-based media file format).

For example, the three-dimensional data acquisition device includes aprocessor and a memory and the processor performs the processesdescribed above using the memory.

A three-dimensional data storage device, a three-dimensional dataacquisition device, and the like according to the embodiments of thepresent disclosure have been described above, but the present disclosureis not limited to these embodiments.

Note that each of the processors included in the three-dimensional datastorage device, the three-dimensional data acquisition device, and thelike according to the above embodiments is typically implemented as alarge-scale integrated (LSI) circuit, which is an integrated circuit(IC). These may take the form of individual chips, or may be partiallyor entirely packaged into a single chip.

Such IC is not limited to an LSI, and thus may be implemented as adedicated circuit or a general-purpose processor. Alternatively a fieldprogrammable gate array (FPGA) that allows for programming after themanufacture of an LSI, or a reconfigurable processor that allows forreconfiguration of the connection and the setting of circuit cellsinside an LSI may be employed.

Moreover, in the above embodiments, the structural components may beimplemented as dedicated hardware or may be realized by executing asoftware program suited to such structural components. Alternatively,the structural components may be implemented by a program executor suchas a CPU or a processor reading out and executing the software programrecorded in a recording medium such as a hard disk or a semiconductormemory.

The present disclosure may also be implemented as a three-dimensionaldata storage method, a three-dimensional data acquisition method, or thelike executed by the three-dimensional data storage device, thethree-dimensional data acquisition device, and the like.

Also, the divisions of the functional blocks shown in the block diagramsare mere examples, and thus a plurality of functional blocks may beimplemented as a single functional block, or a single functional blockmay be divided into a plurality of functional blocks, or one or morefunctions may be moved to another functional block. Also, the functionsof a plurality of functional blocks having similar functions may beprocessed by single hardware or software in a parallelized ortime-divided manner.

Also, the processing order of executing the steps shown in theflowcharts is a mere illustration for specifically describing thepresent disclosure, and thus may be an order other than the shown order.Also, one or more of the steps may be executed simultaneously (inparallel) with another step.

A three-dimensional data storage device, a three-dimensional dataacquisition device, and the like according to one or more aspects havebeen described above based on the embodiments, but the presentdisclosure is not limited to these embodiments. The one or more aspectsmay thus include forms achieved by making various modifications to theabove embodiments that can be conceived by those skilled in the art, aswell forms achieved by combining structural components in differentembodiments, without materially departing from the spirit of the presentdisclosure.

INDUSTRIAL APPLICABILITY

The present disclosure is applicable to a three-dimensional data storagedevice and a three-dimensional data acquisition device.

What is claimed is:
 1. A three-dimensional data storage method,comprising: acquiring one or more units in which an encoded streamgenerated by encoding point cloud data is stored; and storing the one ormore units into a file, wherein the storing includes storing informationin control information for the file, the information indicating thatdata stored in the file is data generated by encoding the point clouddata.
 2. The three-dimensional data storage method according to claim 1,wherein the information further indicates an encoding method used in theencoding of the point cloud data out of a first encoding method and asecond encoding method.
 3. The three-dimensional data storage methodaccording to claim 2, wherein the first encoding method is a scheme forencoding geometry information representing a position of the point clouddata by an N-ary tree, and encoding attribute information with referenceto the geometry information, where N is an integer equal to or greaterthan 2, and the second encoding method is a scheme for generating atwo-dimensional image from the point cloud data, and encoding thetwo-dimensional image using a video encoding method.
 4. Thethree-dimensional data storage method according to claim 1, wherein thefile is in conformity with ISO Based Media File Format (ISOBMFF).
 5. Athree-dimensional data acquisition method, comprising: acquiring a filestoring one or more units in which an encoded stream generated byencoding point cloud data is stored; and acquiring the one or more unitsfrom the file, wherein control information for the file includesinformation indicating that data stored in the file is data generated byencoding the point cloud data.
 6. The three-dimensional data acquisitionmethod according to claim 5, wherein the information further indicatesan encoding method used in the encoding of the point cloud data out of afirst encoding method and a second encoding method.
 7. Thethree-dimensional data acquisition method according to claim 6, furthercomprising: acquiring, with reference to the information, one of dataencoded by the first encoding method and data encoded using the secondencoding method from the point cloud data that is encoded.
 8. Thethree-dimensional data acquisition method according to claim 6, whereinthe first encoding method is a scheme for encoding geometry informationrepresenting a position of the point cloud data by an N-ary tree, andencoding attribute information with reference to the geometryinformation, where N is an integer equal to or greater than 2, and thesecond encoding method is a scheme for generating a two-dimensionalimage from the point cloud data, and encoding the two-dimensional imageusing a video encoding method.
 9. The three-dimensional data acquisitionmethod according to claim 5, wherein the file is in conformity withISOBMFF.
 10. A three-dimensional data storage device, comprising: aprocessor; and memory, wherein, using the memory the processor: acquiresone or more units in which an encoded stream generated by encoding pointcloud data is stored; and stores the one or more units into a file,wherein the storing includes storing information in control informationfor the file, the information indicating that data stored in the file isdata generated by encoding the point cloud data.
 11. A three-dimensionaldata acquisition device, comprising: a processor; and memory, whereinwherein, using the memory, the processor: acquires a file storing one ormore units in which an encoded stream generated by encoding point clouddata is stored; and acquires the one or more units from the file,wherein control information for the file includes information indicatingthat data stored in the file is data generated by encoding the pointcloud data.